|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.23 02:47:00 -
[1]
I'm a bit confused...
I got Yapeal installed, and the databases have updated... But now what? I'm very new to the EVE API, but I was hoping to create a kind of character sheet on my local home server to get acquainted with it and then move on to a bigger community project.
Yapeal is a library of classes in OOP, correct? Which files should I include to pull the information that I need? I guess it's better to explain what I'm looking to do.
For example, I would like to register my character. I would put the userid and API key in two text fields, hit submit, and a new page should display asking which characters I would like to use. I select one, type in the password I would like to use to log into that character, hit submit, and then be taken to a page that displays some basic character information.
Basically, how would I incorporate Yapeal into a web application? I'm not asking anyone to make the application for me, rather to point me in the right direction on which file(s) have functions that can be included and used to pull different types of information. The problem I'm having with Yapeal is that it seems to only run from a terminal; thus, when I complete step one of the registration process (id and key) how would I exchange this information with Yapeal?
Sorry if this post is hard to understand. It's late and I always have trouble explaining things. 
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.23 05:19:00 -
[2]
Edited by: Sable Blitzmann on 23/08/2009 05:22:07 The wiki and docs are few and far between, but I kinda understand now how Yapeal works. It it run on a schedule, and when it is, it updates everything in the database to their current true values, correct?
Great, that's awesome. However, I'm still having a little bit of trouble understanding how to initially create a user. I know you can manually add them to the database, but I would have thought there'd be an easier way to add the account to the database, and from that pull the characters, and from that register a character. I'm still trying to wrap my head around that part of the process. =)
Also, the IGB thing - I thought there was an installer version being released for the IGB, but I read through the topic more carefully and figured out that this is no longer the case.
Questions: What is a good time to schedule Yapeal? Once an hour? Once every 10 minutes? Every minute? And how fast is the updating if I use this in a community site where there's the potential of thousands of users being registered and updated? Will this put a heavy heavy load on my or CCP's server? Also, since you're not pulling data directly from CCP every time you access a characters info, but instead pull it from a local database, how accurate will that be (I'm sure that's depenant on how often I run the cron, yes?)?
I think this project is awesome by the way. Keep up the good work 
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.23 07:55:00 -
[3]
Originally by: Dragonaire Yapeal is made to be ran every minute in a crontab and keeps track of the cachedUntil times itself so it plays nice with the API servers. The data in the database will be update as often as the API allows with a tiny bit of randomness to help disperse bursts of calls to the APIs. As to if the API servers can handle thousands of accounts grabbing all that data that's a better question asked of CCP than of me.
Well, the reason I ask about the server load is because of this: Lets say Yapeal runs every minute. Lets also assume Yapeal is running as a back-end to a web application that serves thousands of EVE's players. Within any given moment, those thousands of EVE players have changing values in their wallet and whatnot. It would seem that to keep the Yapeal database up to date it would have to update thousands of records (maybe more? ) per minute. Now that sounds like a lot to me, but with computers, who knows. Maybe it's nothing. 
Originally by: Dragonaire You put your info into the utilRegistered* tables for any characters and/or corporations you want data for. We are currently working on some changes that should make managing available APIs etc in applications easier as all the settings will be in the DB instead of a mix of the DB and the ini file. The installer is last part that needs updated before it's released in the trunk so people can try it. The main programmer for the installer was busy in RL plus his MySQL server had crashed on him and needed re-installed Hope to have new version out this weekend or this next week at latest.
Thanks for the info; looking forward to testing out the new install.
Originally by: Dragonaire Also look for future version to add a way to call APIs in an 'on demand' basis in addition to the current crontab system. Using that should scale much better for larger web applications while causing less loading of the API servers.
I think everyone would appreciate this. I've looked through the code and it seems like it wouldn't be too difficult to modify bits and pieces here and there so that you can easily include a lot of these classes right into webpage's and applications. For example, and from what I can tell, you already have the classes to call for API info from either fresh from the server or the database using YapealApiRequests(). Any ETA on when something like that would be available?
I really look forward to studying and breaking down this code. You've done a very good job with this cool project. It's been a while since I've been active in coding, and I think I'm gonna start my reintroduction with this 
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.23 16:02:00 -
[4]
Thank you for your helpful and thoughtful responses. =D
Can't wait to see what the devs come up with.
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.25 19:30:00 -
[5]
I have another question relating to SVN...
I'm new to SVN, so i don't really know the mechanics. If I were to add my own notes to the source files, and then I updated to the latest revision using `svn up`, would I lose all my edits? Or will ASVN know to ignore my additions and just add yours?
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.26 00:49:00 -
[6]
lol, I thought that's what might happen. Thanks! 
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.28 04:49:00 -
[7]
Edited by: Sable Blitzmann on 28/08/2009 04:51:44 I'm still playing around with it. I finally got cURL working on my server so I've been testing a lot of things out. Question: the corp stuff only works if you are the CEO of said corp, correct? Because I put in my characters info AND my corps info into the appropriate util* tables, yet when I go to run yapeal.php, it returns errors.
I assume then that I must be CEO of that corp or have some sort of role (of which I do not have...), thus making the corp API's useless to regular corp members...
Do the character APIs export the characters role in his or her corp so that I can use that to narrow down what options are available for that character? For example, if a regular corp member without roles registered on the site, I do not want to insert anything into the utilRegisteredCorp table. If the corp accountant registers, I only want to enter into the `activeapi` column the API's that character can access.
Also, how does yapeal handle character deletions and role removals? If a character was removed from a role, will yapeal update the database to reflect this?
So many question, I know, but I'm very intrigued with this project.
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.28 08:30:00 -
[8]
Thanks for all the great work Dragon.
I do see one corp API that any corp member can access: `corpCorporationSheet` This just gets basic (and from what I can tell, public) details about the corp. So there is a reason to add a corp to the untiRegisteredCorps, even if that character doesn't have any roles. =)
|

Sable Blitzmann
Minmatar Eve University
|
Posted - 2009.08.28 19:42:00 -
[9]
Edited by: Sable Blitzmann on 28/08/2009 19:43:04 EDIT: nvm.
Awesome stuff, btw
|
|
|
|